Skip to main content

Support for multiple downloadable files per product edition

In this release, we have introduced support for attaching and managing multiple downloadable files per product edition, enhancing how product-related content is delivered to end users.

Feature highlights​

  • Attach multiple files per edition: Administrators can now upload and manage various file types (for example - .exe, .zip, .pdf) for each product edition.
  • GraphQL API and S3 integration: Files are managed through product-service GraphQL APIs and uploaded to S3 using pre-signed URLs (max size: 2GB/file; 2-hour expiration).
  • Manual upload only: File uploads must be performed manually through the UI. There is no public API for uploading.
  • Provisioning required: Editions must have provisioning configurations (dummy endpoints allowed). Administrators or developers cannot save editions without this setup in place.
  • No file rename or notifications: Administrators or developers cannot rename files after upload (must delete and re-upload). No automated notifications are sent for new or updated files.
  • Legacy deprecation: Legacy Downloadable Products are deprecated. Use Edition Files going forward.

Customer impact​

  • Administrators or Developers: Gain the ability to associate multiple files with product editions, improving the delivery of setup files, manuals, and supporting assets.
  • End users: Can access and download these files from the MyApps page after completing checkout (1-click install is not supported).

UI updates​

  • Manage Apps
    New Download Files tab for each edition:
    • Displays files in a paginated table (5 per page by default)
    • Provides actions for Download, Update, and Delete
  • MyApps page
    New download gear icon for all applications:
    • Clicking shows a list of downloadable edition files (if any)
  • Edition Panel
    After edition creation, a file upload section appears:
    • Supports uploading multiple files per edition
    • No file rename option—delete and re-upload required
    • UI reflects provisioning requirements and file presence

Feature enablement

No feature enablement is required.

Setting enablement

No setting enablement is required.

Documentation

Refer to the following:

Was this page helpful?

Tell us more…

Help us improve our content. Responses are anonymous.

Thanks

We appreciate your feedback!